Conversation
|
I'm not sure about using Should we lock the liquid-c SHA in the gemfile? |
|
Also, it will fail on non-MRI rubies :( |
|
Hmm good points |
|
nice 2x2 test matrix, quadruple error messages if you screw up something globally 😈 In terms of version issues, maybe gate it by an environment variable that is set in CI? |
There was a problem hiding this comment.
Nitpick, but $stderr.puts here?
|
👍 |
|
How about instead of using master, we use the latest released version of the liquid-c gem? |
|
@fw42 I think that still has the same problem, and also makes updating liquid and liquid-c in tandem difficult. |
|
Hm I don't like the idea of hardcoding a liquid/c ref/version, we will forget to bump that. |
Run tests with latest liquid/c gem
Turns out #592 is actually broken if liquid/c is present.
This PR makes it so that we run tests twice, once with and once without liquid/c enabled.
(Tests in this PR are going to fail for now. Justin is working on a fix in liquid/c.)
@pushrax @trishume